Repository navigation
docs(databricks): Unity Catalog comments, product tags and certification in 0.28.0 - #202
Merged
Merged
Conversation
…ion in 0.28.0 - providers/databricks.md: table and column comments from the contract (a dbt-written table keeps dbt's), the product's identity tags and the fluid_sensitivity column tags, certification through system.certification_status (certified from the label, deprecated from lifecycle.state), the limits and refusal codes, and the #835 changes: the landing's clean-up, the dry-run's superseded-function lines and the sovereignty reason. Live claims follow HONESTLY_TESTED.md's 2026-11-04 run; an identity holding only ASSIGN was not tried. - advanced/error-codes.md: the databricks-* kinds behind unsupported_binding, with what triggers each and the fix (three new in 0.28.0, two older with new triggers).
2 tasks done
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents what forge-cli 0.28.0 does on Databricks (forge-cli #831 and #835). forge_docs#201 only summarised it in
upgrading.md.docs/providers/databricks.mdpersist_docs), andfluid validatewarns when the contract describes it.fluid_sensitivitycolumn tags, at most 1,000 per table.system.certification_status.certifiedcomes from the label (case ignored), anddeprecatedfromlifecycle.state, which wins. Any other label value is refused. The ASSIGN permission on that governed tag comes from Databricks' documentation and was not tried with a non-admin identity.databricks-tag-collision(only for keys the contract states),databricks-tag-value-too-long,databricks-tags-too-many,databricks-comment-unsafe,databricks-certification-invalid.fluid apply --mode dry-runlisting superseded function drops;HONESTLY_TESTED.md's 2026-11-04 row: what was read back live, and what was not re-run.docs/advanced/error-codes.md: thedatabricks-*kinds behindunsupported_binding, with trigger and fix. Three are new in 0.28.0;tag-collisionandtags-too-manyare older and gained new triggers.Checks
data-product-forge[databricks]==0.28.0from PyPI (Python 3.11), all exit 0:check_cli_docs.pycheck_providers.pycheck_cli_docs.py --markers-onlygen_contract_reference.py --checknpm run docs:buildcheck-dist-links.mjsvalidate,generate iac, the refusal kind lines, the plan note). Its 7 corrections are applied. No Databricks workspace was available, so the landing clean-up and the dry-run function lines are described from the code.